Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

models wrapping + sdk integration with generated client #17071

Conversation

mshaban-msft
Copy link
Contributor

No description provided.

@check-enforcer
Copy link

check-enforcer bot commented Mar 3, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@mshaban-msft
Copy link
Contributor Author

@kristapratico

Copy link
Member

@kristapratico kristapratico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is work in progress, just some early feedback. looking good :)

@@ -152,7 +162,8 @@ def get_supported_glossary_formats(self, **kwargs):
:rtype: List[FileFormat]
"""

return self._client.document_translation.get_glossary_formats(**kwargs)
glossary_formats = self._client.document_translation.get_glossary_formats(**kwargs)
return FileFormat._from_generated_list(glossary_formats)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it work to fold the helper methods into one like this?

return [FileFormat._from_generated(glossary_format) for glossary_format in glossary_formats.value]

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i used to do it inline, but i thought it's much cleaner if i created "_from_generated_list()" to process lists
instead of having to same code for the same object over and over

def _from_generated(cls, file_format):
return cls(
format=file_format.format,
file_extentions=file_format.file_extentions,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
file_extentions=file_format.file_extentions,
file_extensions=file_format.file_extensions,

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

?!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

spelling

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry :)

@kristapratico kristapratico deleted the branch Azure:document-translation March 4, 2021 21:32
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this pull request Mar 28, 2022
[Hub Generated] Review request for Microsoft.Confluent to add version stable/2021-12-01 (Azure#17070)

* Adds base for updating Microsoft.Confluent from version preview/2021-09-01-preview to version 2021-12-01

* Updates readme

* Updates API version in new specs and examples

* Fixing spellcheck and updating readme files (Azure#17071)

* Update confluent.json (Azure#18254)

Fixing linting errors

* Update confluent.json for LintDiff fixes (Azure#18261)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants